-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added option to skip watting for start command #167
Conversation
Promoting this feature again since we have now 2 PRs for this - @Eusebius1920 referenced previous PR implementing the same. Just to give perspective - other debuggers have features to start debugging in waiting or non-waiting mode:
Any chance to merge this? |
@iggycoder @FabioMR this PR looks much safer than #145, we'll discuss it |
@ViugiNick Sure, we can discuss it. What can i do to get this PR merged in? |
@FabioMR @iggycoder, For now, it remains only to wait for a colleague who has rights to merge PR's in this repo |
Any updates regarding the colleague/merge of the PR? |
@FabioMR Could you please clarify, why do you need this change in gemspec? |
@ViugiNick It was just to remove a deprecation warning message. If it is a problem, we can change it back. |
@FabioMR @iggycoder merged and ruby-debug-ide-0.7.1.beta1 released |
I always keep the server running and use VSCode to attach to the active process.
So it is more useful to skip the "wait for a start command" line.